Adjustment of infusion user interface upon docking event

ABSTRACT

A patient care system includes a control unit capable of coupling with multiple modular medical devices. A modular medical device can be coupled with the control unit, wherein the behavior of the modular medical device automatically adjusts based on the status of being coupled or un-coupled with the control unit.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.14/175,846 filed on Feb. 7, 2014, issuing on Jan. 17, 2017 as U.S. Pat.No. 9,545,475. The disclosure of which is hereby incorporated byreference in its entirety

BACKGROUND

Infusion pump and sensing device systems are widely used in the medicalfield for infusing a fluid, such as a medication, to a patient in theenvironment of intensive care units, cardiac care units, operating roomsor trauma centers. Several types of infusion pump systems permit theinfusion of several medications using pumps that are modularly coupledto one another, as it may often be necessary to simultaneously infuseinto the patient several different kinds of fluids. Some of the severaltypes of fluids, such as drugs, may not be directly compatible with eachother and therefore need to be infused into the patient at differentpoints of the body or at different times.

In this regard, there exist modular systems in which a pump module canbe selectively attached, both physically and electrically, to a controlunit.

SUMMARY

The control unit controls the operation of one or more pump modulesattached to it. The control unit and the pump module may both include anintegral or attachable display unit that is configured to displayinformation related to infusion of fluid. The control unit may have adisplay that is larger, smaller or the same size as the pump module and,likewise, the user input mechanism (e.g. touch panel) of the controlunit may be larger, smaller or the same size as the user input mechanismof the pump module. As the pump module is typically portable, and wouldgenerally have less display space and space for the user inputmechanism, when coupled to the control unit, more detailed informationregarding an infusion may be viewable.

It is desirable to take advantage of the capabilities of the controlunit when the pump module is docked to the control unit. A smallerdisplay on the pump module may be used to display information specificto an infusion running on the device when attached to the control unit.The full functionality of the user input mechanism on the pump modulemay be utilized when the pump module is detached from the control unit,such as in a transport mode.

In one aspect, there is disclosed a method of managing a modularinfusion pump device, comprising: coupling a modular infusion pump to acontrol unit; establishing a data link between the modular infusion pumpand control unit upon coupling the modular infusion pump to the controlunit; transferring data between the modular infusion pump and thecontrol unit as a result of the coupling control unit; and adjusting thebehavior of the modular infusion pump and the control unit as a resultof coupling the modular infusion pump to the control unit.

In another aspect, there is disclosed a patient care system, comprising:a control unit capable of coupling with multiple modular medicaldevices; and a modular medical device capable of being coupled with thecontrol unit, wherein the behavior of the modular medical deviceautomatically adjusts based on the status of being coupled or un-coupledwith the control unit.

The details of one or more variations of the subject matter describedherein are set forth in the accompanying drawings and the descriptionbelow. Other features and advantages of the subject matter describedherein will be apparent from the description and drawings, and from theclaims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B show front and side views, respectively, of a portion ofa patient care system showing two fluid infusion pump modules mountedbelow a control unit, and the displays and control keys of each, withthe control unit being capable of programming both infusion pumps;

FIG. 2 diagrams the workflow of attaching and detaching a standalonepump module to a control unit as well as a transition of the userinterface elements from one component to the next.

DETAILED DESCRIPTION

Disclosed is a medical fluid infusion system configured for pumping afluid to a patient, such as in a hospital environment. The systemincludes one or more modular infusion pump devices each of which isconfigured to be removably coupled to a control unit. The control unitand the one or more modular pump devices each include a display that isconfigured to display information. The information may be, for example,operating parameters of the pump device and alert indications and alarmmessages although the information may vary widely. The control unit andthe modular pump devices also each include one or more input mechanismsfor initiating, modifying, or otherwise programing an infusion scenariofor a patient.

As described in detail below, the infusion system is configured tomodify the information that is displayed on the modular pump device andthe control unit based on whether or not the modular pump device isdocked or otherwise coupled to the control unit. The behavior of thecontrol unit and the modular pump device may also be modified based onwhether or not the modular pump device is docked or otherwise coupled tothe control unit. For example, the responsibility for initiation ormodification of infusion may be delegated to the control unit or to oneor more of the modular pump devices. Or the responsibility may beallocated between two or more of the devices. This permits the user totake advantage of the varied capabilities of the control unit or amodular pump device in programming or initiating an infusion.

Referring now in more detail to the drawings in which like referencenumerals refer to like or corresponding elements among the severalviews, there is shown in FIGS. 1A and 1B a patient care system 10 havingmodular infusion pumps 20. Each of the modular infusion pumps 20mechanically, electrically and/or communicatively couples to a controlunit 25, which is configured to provide control and/or monitoringcapabilities for each of the one or more infusion pumps that areattached to it. The coupling between the infusion pumps and the controlunit may vary and may be, for example, a mechanical or galvanic couplingor it may be a wireless, inductive or optical coupling. In any event,the control unit 25 and the respective infusion pumps are configured todetect when a coupling occurs and may modify the behavior of therespective devices accordingly, as described in detail below.

Fluid supplies may be attached or otherwise coupled to the system andmay take various forms and may include bags, syringes or other types ofcontainers. In certain embodiments, a single-channel infusion pump 20 isused to infuse each of the fluids of the fluid supplies into thepatient. In other embodiments, a multi-channel infusion pump (such asthe MedSystem® III Infusion Pump (CareFusion, San Diego, Calif.)) isused to infuse fluids into the patient. The infusion pumps are flowcontrol devices that will act on a respective fluid line to move thefluid from the fluid supply through the fluid line to the patient. Eachpump, or each channel within a pump, can be individually set to thepumping or operating parameters required for infusing the particularmedical fluid from the respective fluid supply into the patient at theparticular rate prescribed for that fluid by the physician. Such medicalfluids may comprise drugs or nutrients or other fluids.

Referring to FIG. 1A, a view of the front of the infusion pumps 20 isshown. A display 30 such as an LCD display, is located in plain view oneach of the infusion pumps 20 and may be used to visually communicatevarious information relevant to the pump, such as alert indications(e.g., alarm messages). The display 30 of the infusion pumps 20 may varyin size relative to the display 35 of the control unit 25. For example,the display 30 of the infusion pump 20 may often be smaller than thedisplay 35 of the control unit 25 given that the infusion pumps areportable. The smaller display 30 may be lighter in weight than thedisplay 35.

One or more control keys 40 and a user input mechanism (e.g. touchpanel) may be included on the infusion pumps for programming andcontrolling operations of the infusion pump as desired. The infusionpumps 20 may also include audio alarm equipment in the form of a speaker45, which, in certain embodiments, may only be used when the respectiveinfusion pump is un-coupled from the control unit 25, while in transportmode.

In the embodiment shown, the control unit 25 is positioned above theattached infusion pumps 20. Other devices or modules, including anotherinfusion pump, may be attached below the first modular infusion pump, asshown in FIGS. 1A and 1B. In such a system, each attached pumprepresents a pump channel of the overall patient care system 10. In anembodiment, the control unit 25 is used to provide an interface betweenthe infusion pumps 20 and external devices as well as to provide most ofthe operator interface for the infusion pump 5. In other embodiments,the control unit 25 may be configured such that that infusion pumpmodules 25 are attached above, below or to the side of the control unit.

As mentioned, the control unit 25 includes a display 35 for visuallycommunicating various information, such as the operating parameters ofthe infusion pumps 20 and alert indications and alarm messages. Thecontrol unit 25 may also include a speaker (not shown) to provideaudible alarms. The control unit 25 or any other module also has variousinput devices in this embodiment, including control keys, touch panel,and a bar code or other scanner or reader for scanning information froman electronic data tag relating to the infusion, the patient, the caregiver, or other. The control unit 25 may also have a communicationssystem (not shown) which may communicate with external equipment such asa medical facility server or other computer and with a portableprocessor, such as a handheld portable digital assistant (“PDA”), or atablet or laptop-type of computer, or other information device that acare giver may have to transfer information as well as to download druglibraries to a control unit or pump.

The communications system may take the form of a radio frequency (“RF”)system, an optical system such as infrared, a Blue Tooth system, orother wired or wireless system. The bar code scanner and communicationssystem may alternatively be included integrally with the infusion pump20, such as in cases where a control unit is not used, or in addition toone with the control unit. Further, information input devices need notbe hard-wired to medical instruments, information may be transferredthrough a wireless connection as well.

In some embodiments, the infusion pump module may also have acommunication system that may take the form of a radio frequency (“RF”)system, an optical system such as infrared, a Blue Tooth system, orother wired or wireless system.

FIGS. 1A and 1B show two infusion pumps 20 connected to the control unit25. It should be appreciated that more (or less) infusion pumps may beconnected to the control unit 25. Additionally, other types of modulesmay be connected to the control unit 25. Infusion pump modules typesthat are included within the scope of this disclosure include, but arenot limited to Large Volume Parenteral 5 & 6, Syringe, PatientControlled Analgesic (“PCA”), Enteral and Epidural modules.Additionally, patient monitoring modules may be attached physicallyand/or wirelessly to the control unit 25. The patient monitoring moduleswould be accessible and programmable by the control unit in the samefashion as the infusion pump modules.

Adjustment of User Interface Upon Coupling of Infusion Pump to ControlUnit

As discussed, the infusion system 10 is configured to modify theinformation that is displayed on the infusion pump(s) 20 and the controlunit 25 based on whether or not a modular infusion pump 20 is docked orotherwise coupled to the control unit 25. The infusion system may alsoinitiate a transfer of data between one or more of the infusion pumps 20and the control unit upon coupling of an infusion pump and the controlunit 25. The data may vary and may include, for example, the patient'sname, hospital identification number, and other information such as thepatient's age, weight, condition, and allergies. The data may alsoinclude, for example, the patient's MAR (medication administrationrecord), a drug identifier, a drug concentration, a diluent fluididentifier, a dose or flow rate, other pumping-related parameters,contra-indicated medications/conditions, alarm conditions, etc.Moreover, the system 10 may be configured to modify the type of datathat is displayed or how the data is displayed (font size, color,brightness, etc.) between the displays of the control unit and infusionpumps as well as how notification of alarm conditions is handled.

With reference to FIG. 2, there is now described a method of modifyingthe behavior of the modular infusion pump and the control unit basedupon a whether or not the modular infusion pump and control unit arecoupled to one another. In a first step 400, a practitioner activates amodular infusion pump in a standalone state. In such a standalone state,the infusion pump handles and manages the infusion of fluid to apatient. This includes keeping track of and displaying relevant data onits own display.

In step 405, a practitioner couples the modular infusion pump to thecontrol unit. As mentioned, the coupling may be a direct or indirectmechanical coupling or it may be a wireless coupling. In this regard, amechanical or wireless data link between the devices is established. Inan embodiment, the modular infusion pump is attached or docked to a rackassembly that couples the modular infusion pump to the control unit. Themodular infusion pump or the control unit may include a mechanical orsoftware mechanism that triggers an alert upon the coupling event.

In a next step 410, a data transfer occurs between the modular infusionpump and the control unit. The type of data that is transferred may varyas discussed above. Data may be transferred from the modular infusionpump to the control unit, from the control unit to the modular infusionpump, or both. The data transfer may take advantage of increasedcomputer memory capabilities between the devices, as well as variationsin mechanical capabilities (such as speakers, display size, etc.)between the devices.

In an embodiment, the display of data, such as a user interface, isadjusted between the modular infusion pump and the control unit uponcoupling of the modular infusion pump to the control unit. For example,the user interface of the control unit may be modified to displayadditional data related to the operation of the modular infusion pumpwhereas the user interface of the modular infusion pump is modified todisplay less data. The user interfaces of the respective devices may bemodified in a variety of manners such as to share responsibility fordisplaying data related to the modular infusion pump. This can takeadvantage of the larger screen size, if present, of the control unitrelative to the infusion pump. In an embodiment, certain components ofthe user interface remain with the modular infusion pump regardless ofwhether the modular infusion pump is coupled to the control unit. Forexample, the ability to pause infusion may remain with the controls ofthe modular infusion pump.

Alarm management features may also be modified between the modularinfusion pump and the control unit upon coupling of the infusion moduleto a program module. For example, the control unit may take overresponsibility for initiating audio or visual alarm signals from themodular infusion pump. In this regard, the control unit may receivealarm notifications from multiple modular infusion pumps that areattached to it. The control unit may rank or otherwise prioritize themultiple alarm signals and display or voice an alarm or alarms based onthe rankings, such as an alarm that is deemed to be most important. Thecontrol unit may also take over responsibility for confirmation oracknowledgement of the alarm from the modular infusion pump. In such asituation, the clinician would acknowledge an alarm by interfacing withthe control unit rather than with the modular infusion pump.

The responsibility for initiation or modification of infusion may alsobe modified between the modular infusion pump and the control unit uponcoupling or uncoupling of the modular infusion pump to the control unit.Infusion programming or initiation responsibility may be delegated tothe control unit or to one or more of the modular pump devices or it maybe allocated between two or more of the devices. The user may then takeadvantage of the varied capabilities of the control unit or a modularpump device for programming an infusion. This may improve or augment theworkflow efficiency during initiation of an infusion or entry ofinfusion parameters. For example, the user may take advantage of thepossibly larger display and/or richer interactivity capabilities of thecontrol unit versus the modular infusion pump. The larger display unitand/or input mechanisms on the control unit may also allow the use ofmore complex protocols that might be impractical or inconvenient on thesmaller landscape of the modular infusion pump.

With reference again to FIG. 2, in a next step 415, the modular infusionpump is decoupled from the control unit. As discussed, the modularinfusion pump or the control unit may include a mechanical or softwaremechanism that triggers an alert upon the coupling event or decouplingevent. The method then proceeds to step 420, where the device againinitiate a data transfer and re-allocation of duties. For example, thecontrol unit will revert responsibility for display of data and alarmmanagement to the modular infusion pump.

One or more aspects or features of the subject matter described hereinmay be realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations may include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device (e.g., mouse, touch screen, etc.), andat least one output device.

These computer programs, which can also be referred to programs,software, software applications, applications, components, or code,include machine instructions for a programmable processor, and can beimplemented in a high-level procedural and/or object-orientedprogramming language, and/or in assembly/machine language. As usedherein, the term “machine-readable medium” refers to any computerprogram product, apparatus and/or device, such as for example magneticdiscs, optical disks, memory, and Programmable Logic Devices (PLDs),used to provide machine instructions and/or data to a programmableprocessor, including a machine-readable medium that receives machineinstructions as a machine-readable signal. The term “machine-readablesignal” refers to any signal used to provide machine instructions and/ordata to a programmable processor. The machine-readable medium can storesuch machine instructions non-transitorily, such as for example as woulda non-transient solid state memory or a magnetic hard drive or anyequivalent storage medium. The machine-readable medium can alternativelyor additionally store such machine instructions in a transient manner,such as for example as would a processor cache or other random accessmemory associated with one or more physical processor cores.

These computer programs, which can also be referred to programs,software, software applications, applications, components, or code,include machine instructions for a programmable processor, and can beimplemented in a high-level procedural language, an object-orientedprogramming language, a functional programming language, a logicalprogramming language, and/or in assembly/machine language. As usedherein, the term “machine-readable medium” refers to any computerprogram product, apparatus and/or device, such as for example magneticdiscs, optical disks, memory, and Programmable Logic Devices (PLDs),used to provide machine instructions and/or data to a programmableprocessor, including a machine-readable medium that receives machineinstructions as a machine-readable signal. The term “machine-readablesignal” refers to any signal used to provide machine instructions and/ordata to a programmable processor. The machine-readable medium can storesuch machine instructions non-transitorily, such as for example as woulda non-transient solid state memory or a magnetic hard drive or anyequivalent storage medium. The machine-readable medium can alternativelyor additionally store such machine instructions in a transient manner,such as for example as would a processor cache or other random accessmemory associated with one or more physical processor cores.

To provide for interaction with a user, the subject matter describedherein can be implemented on a device having a display device, such asfor example a liquid crystal display (LCD) monitor for displayinginformation to the user and a keyboard and a input device, such as forexample a mouse or a trackball, by which the user may provide input tothe device. Other kinds of devices can be used to provide forinteraction with a user as well. For example, feedback provided to theuser can be any form of sensory feedback, such as for example visualfeedback, auditory feedback, or tactile feedback; and input from theuser may be received in any form, including, but not limited to,acoustic, speech, or tactile input. Other possible input devicesinclude, but are not limited to, touch screens or other touch-sensitivedevices such as single or multi-point resistive or capacitive trackpads,voice recognition hardware and software, optical scanners, opticalpointers, digital image capture devices and associated interpretationsoftware, and the like.

The subject matter described herein can be embodied in systems,apparatus, methods, and/or articles depending on the desiredconfiguration. The implementations set forth in the foregoingdescription do not represent all implementations consistent with thesubject matter described herein. Instead, they are merely some examplesconsistent with aspects related to the described subject matter.Although a few variations have been described in detail above, othermodifications or additions are possible. In particular, further featuresand/or variations can be provided in addition to those set forth herein.For example, the implementations described above can be directed tovarious combinations and subcombinations of the disclosed featuresand/or combinations and subcombinations of several further featuresdisclosed above. In addition, the logic flow(s) when depicted in theaccompanying figures and/or described herein do not necessarily requirethe particular order shown, or sequential order, to achieve desirableresults. Other implementations may be within the scope of the followingclaims.

1-21. (canceled)
 22. A pump system, comprising: a modular infusion pumphaving a microprocessor, wherein the modular infusion pump couples to apatient via a fluid line, wherein the modular infusion pump couples to acontrol unit and wherein data is transferred between the modularinfusion pump and the control unit when the modular infusion pump andthe control unit are coupled to one another, wherein the microprocessoris configured to: detect that the modular infusion pump has been coupledto or uncoupled from the control unit; cause the modular infusion pumpto automatically undergo an adjustment in behavior based on the statusof being coupled to or un-coupled from the control unit and wherein thebehavior of the modular infusion pump adjusts differently depending onwhether the infusion modular pump is coupled to the control unitwirelessly, electrically or mechanically, and wherein the adjustment inbehavior comprises a modification of a user interface of the modularinfusion pump.
 23. The pump system of claim 22, wherein the modularinfusion pump has a first display and the control unit has a seconddisplay.
 24. The pump system of claim 23, wherein the first display andthe second display are different sizes.
 25. The pump system of claim 22,wherein data is transferred from the modular infusion pump to thecontrol unit when the modular infusion pump and the control unit arecoupled to one another.
 26. The pump system of claim 22, wherein data istransferred from the control unit to the modular infusion pump when themodular infusion pump and the control unit are coupled to one another.27. The pump system of claim 22, wherein the data includes infusionprogram data.
 28. The pump system of claim 22, further comprising thecontrol unit.
 29. A non-transitory computer readable medium comprisinginstructions executable by a processor to cause a modular infusion pumpof a medical fluid delivery system to: detect that the modular infusionpump has been coupled to or uncoupled from a control unit; cause themodular infusion pump to automatically undergo an adjustment in behaviorbased on the status of being coupled to or un-coupled from the controlunit and wherein the behavior of the modular infusion pump adjustsdifferently depending on whether the infusion modular pump is coupled tothe control unit wirelessly, electrically or mechanically, and whereinthe adjustment in behavior comprises a modification of a user interfaceof the modular infusion pump.
 30. The non-transitory computer readablemedium of claim 29, wherein the modular infusion pump has a firstdisplay and the control unit has a second display.
 31. Thenon-transitory computer readable medium of claim 30, wherein the firstdisplay and the second display are different sizes.
 32. Thenon-transitory computer readable medium of claim 29, wherein data istransferred from the modular infusion pump to the control unit when themodular infusion pump and the control unit are coupled to one another.33. The non-transitory computer readable medium of claim 29, whereindata is transferred from the control unit to the modular infusion pumpwhen the modular infusion pump and the control unit are coupled to oneanother.
 34. The non-transitory computer readable medium of claim 29,wherein the data includes infusion program data.
 35. The non-transitorycomputer readable medium of claim 29, wherein a user input mechanism onthe modular infusion pump is disabled upon coupling with the controlunit.
 36. The non-transitory computer readable medium of claim 29,wherein the adjustment in behavior further comprises an allocation ofalarm management duties between the control unit and the modularinfusion pump.
 37. The non-transitory computer readable medium of claim29, wherein the adjustment in behavior further comprises assigningresponsibility for issuing alarm notifications to the control unit. 38.The non-transitory computer readable medium of claim 29, wherein theadjustment in behavior further comprises assigning responsibility foracknowledging alarm notifications to the control unit.
 39. Thenon-transitory computer readable medium of claim 29, wherein theadjustment in behavior further comprises assigning responsibility forinfusion programming for the coupled modular infusion pump to thecontrol unit.
 40. The non-transitory computer readable medium of claim29, wherein the adjustment in behavior further comprises switching froma battery-powered mode to a recharging mode when the modular infusionpump is in electrical communication with the control unit.
 41. Thenon-transitory computer readable medium of claim 29, wherein theadjustment in behavior further comprises allocating responsibility forprogramming of infusion parameters between the modular infusion pump andthe control unit.